🤔 This feels maybe too opinionated...

since you could have logic associated with it changing...that this is now going to trigger...

After checking, I confirmed that @change was being triggered even when the x-model value remained the same. To address this, I’ve updated the logic to dispatch the change event only when the current value is missing from the updated options list.

If you feel that triggering the event upon an x-model change is problematic, I’d like to share my perspective. I viewed this approach as being more aligned with the declarative nature that Alpine.js pursues, where the UI reacts naturally to state changes.